Service agreement performance validation in a cloud hosted environment

ABSTRACT

Service agreement performance validation includes receiving a request for access to an application from a client system. The application is hosted by a data center in a network-hosted computing environment. The service agreement performance validation also includes querying a global positioning system receiver for geographic location information of the data center, receiving the geographic location information from the global positioning system receiver, transmitting the geographic location information to the client system, and providing access to the application.

BACKGROUND

The present invention relates to network computing, and morespecifically, to service agreement performance validation andconformance in a cloud hosted environment.

Network-managed data by service providers has become increasinglypopular, as the amount of data utilized by business enterprises,organizations, and even by some individuals has increased. The costsassociated with hardware and storage devices, as well as theirassociated bandwidth requirements have made network-managed solutionsmore desirable.

Service agreements (also known as service level agreements, or SLAs)between a host provider and a customer typically include terms thatspecify a quality of service (QoS) that is to be expected for activitiesconducted within the hosting environment. For example, costs forreceiving host services can vary depending on the number of applicationshosted, the number of instances of an application running (e.g., forredundancy and load balancing), and the times and site locations of thehosting (e.g., the data center selected for the hosting). While theservice agreements spell out these terms, currently there is no way forthe host provider to assure the customer that performance under theterms of the agreement is fully satisfied. Likewise, there is no way forthe customer to validate compliance by the host provider.

SUMMARY

According to one embodiment of the present invention, a method isprovided. The method includes receiving a request for access to anapplication from a client system. The application is hosted by a datacenter in a network-hosted computing environment. The method alsoincludes querying a global positioning system receiver for geographiclocation information of the data center, and receiving the geographiclocation information from the global positioning system receiver. Themethod further includes transmitting the geographic location informationto the client system, and providing access to the application.

According to another embodiment of the present invention, a system isprovided. The system includes a computer processor and logic executableby the computer processor. The logic is configured to implement amethod. The method includes receiving a request for access to anapplication from a client system. The application is hosted by a datacenter in a network-hosted computing environment. The method alsoincludes querying a global positioning system receiver for geographiclocation information of the data center, and receiving the geographiclocation information from the global positioning system receiver. Themethod further includes transmitting the geographic location informationto the client system, and providing access to the application.

According to a further embodiment of the present invention, a computerprogram product is provided. The computer program product includes acomputer-readable storage medium having instructions embodied thereon,which when executed by a computer, causes the computer to implement amethod. The method includes receiving a request for access to anapplication from a client system. The application is hosted by a datacenter in a network-hosted computing environment. The method alsoincludes querying a global positioning system receiver for geographiclocation information of the data center, and receiving the geographiclocation information from the global positioning system receiver. Themethod further includes transmitting the geographic location informationto the client system, and providing access to the application.

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention. For a better understanding of the invention with theadvantages and the features, refer to the description and to thedrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter which is regarded as the invention is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The forgoing and other features, and advantages ofthe invention are apparent from the following detailed description takenin conjunction with the accompanying drawings in which:

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention;

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention;

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention;

FIG. 4 depicts a block diagram of a system upon which service agreementperformance validation for network-hosted services may be implementedaccording to an embodiment of the present invention;

FIG. 5 depicts a block diagram of a sample data center associated withthe system of FIG. 4 according to an embodiment of the presentinvention;

FIG. 6 is a flow diagram of a process for implementing service agreementperformance validation for network-hosted services according to anembodiment of the present invention;

FIG. 7 is a graphical depiction of a location map according to anembodiment of the present invention;

FIG. 8 depicts a user interface screen illustrating a view of serviceagreement non-conformances according to an embodiment of the presentinvention;

FIG. 9 is a flow diagram of a process for implementing service agreementperformance validation for network-hosted services according anotherembodiment of the present invention; and

FIG. 10 is a graphical depiction of a location map according to theembodiment shown in FIG. 9.

DETAILED DESCRIPTION

Exemplary embodiments relate to service agreement performance validationprocesses (also referred to herein as “performance validationprocesses”) in a network-hosted computing environment, which providetransparency to customers utilizing network-hosted computing services interms of validating compliance with terms set forth in the customers'service agreements. The performance validation processes likewiseprovides the ability for network-hosted computing providers to offerassurances to their customers that performance of the network-hostedcomputing activities is implemented according to the terms of theirservice agreements. In addition, the performance validation processesprovides options for customers to view performance activities, as wellas any non-conformances resulting from these activities, and to take anydesired actions in response thereto. These and other features of theperformance validation processes will now be described.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed (e.g., any client-server model).

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client systems through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via I/O interfaces22. Still yet, computer system/server 12 can communicate with one ormore networks such as a local area network (LAN), a general wide areanetwork (WAN), and/or a public network (e.g., the Internet) via networkadapter 20. As depicted, network adapter 20 communicates with the othercomponents of computer system/server 12 via bus 18. It should beunderstood that although not shown, other hardware and/or softwarecomponents could be used in conjunction with computer system/server 12.Examples, include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID systems,tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide)

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one embodiment, one or both of the hardware and software layer 60 andthe virtualization layer 62 may include edge components, such as a webserver front end and image cache, as well as an image library store,e.g., in a high-performance RAID storage area network (SAN).

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security (not shown) provides identity verificationfor cloud consumers and tasks, as well as protection for data and otherresources. User portal provides access to the cloud computingenvironment for consumers and system administrators. Service levelmanagement provides cloud computing resource allocation and managementsuch that required service levels are met. Service Level Agreement (SLA)planning and fulfillment provide pre-arrangement for, and procurementof, cloud computing resources for which a future requirement isanticipated in accordance with an SLA. In one exemplary embodiment,control logic 70 in the management layer 64 implements the exemplaryperformance validation processes described herein; however, it will beunderstood that the control logic 70 may be implemented in any layer.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and a mobile desktop for mobile devices (e.g., 54A, 54C, and54N, as well as mobile nodes 10 in cloud computing environment 50)accessing the cloud computing services.

The control logic 70 includes one or more algorithms to implementembodiments described herein to provide performance validationprocesses. In an embodiment, the control logic 70 is coupled to and/orresides in the memory 28 shown in FIG. 1. In addition, embodiments ofthe control logic 70 may include one or more program modules 42 of theprogram/utility 40 shown in FIG. 1. In a further embodiment, the controllogic 70 is part of the management layer 64 and is executed on hardwarelocated in the hardware and software layer 60.

A portion of the exemplary performance validation processes may beimplemented by a computer device (e.g., local computing devices 54A-54Nof FIG. 2), as a cloud consumer, that is configured to receive locationinformation for one or more data centers from which network-hostedcomputing services are provided. In addition, a portion of the exemplaryperformance validation processes services are performed by at least onenode (e.g., one or more of the nodes 10 in the cloud computingenvironment 50 (shown in FIGS. 1 and 2). In one embodiment, the controllogic 70 receives the location information from a global positioningsystem (GPS) residing in a data center. The location information may bereceived at the data center GPS from a satellite. Other information canbe provided to the cloud consumer as well, such as data centeridentification, application identification, instance identification,etc. An application agent executing on the computer device processesthis information and provides a view (e.g., map, chart, table, etc.) ofthe processed information. These and other aspects of the performancevalidation processes will now be described with respect to FIGS. 4-10.

Turning now to FIG. 4, a system 400 upon which the performancevalidation processes may be implemented will now be described. Thesystem of FIG. 4 depicts a network-hosted provider system 402 (alsoreferred to herein as “provider system”) which, in turn, includes datacenters 410 a-410 n distributed over networks 408, through which theprovider system provides network-hosted computing services to consumers(e.g., cloud computing). Each of the data centers 410 a-410 n may bedistributed throughout various wide-spread geographic locations. Thedata centers 410 a-410 n may include various computer systems, storagedevices, and related resources similar to the nodes 10 described incloud computing environment 50 (FIG. 2).

Also shown in FIG. 4 are a client system 404 and a satellite 406, bothof which are communicatively coupled to the networks 408. The clientsystem 404 represents a cloud consumer or end user of the network-hostedcomputing services provided by the provider system 402. The clientsystem 404 may be implemented similar to the local computing devices 54shown in FIG. 2. In an embodiment, the client system 404 executes anapplication agent 414 to facilitate the performance validation processesdescribed herein.

Turning now to FIG. 5, a detailed implementation of a data center 500will now be described. The data center 500 corresponds to any one of thedata centers 410 a-401 n described in FIG. 4. The data center 500includes a plurality of computer systems 502 a-502 n, which may behigh-speed computer processors, such as servers or mainframe computers,capable of handling a high volume of computing activities conducted byend users of the network-hosted computing services. The computer systems502 a-502 n may each execute a number of applications 508 a-508 n,respectively, as well as control logic 510 a-510 n, respectively. Thecontrol logic 510 a-510 n corresponds to the program modules 42 of FIG.1 and the control logic 70 described in FIG. 3. The control logic 510a-510 n implements the exemplary performance validation processesdescribed herein. While the control logic 510 a-510 n is shown in FIG. 5as executable by each of the computer systems 502 a-502 n, it will beunderstood that a single control logic application may be implemented onone of the computer systems 502 a-502 n in a supervisory capacity withrespect to the remaining computer systems 502 a-502 n.

The computer systems 502 a-502 n may be communicatively coupled torespective storage devices 512 a-512 n, as well as a network bus 506.The storage devices 512 a-512 n may store application data, serviceagreements, and logs, as will be described further herein. A GPS system504 is also coupled to the network bus 506. The GPS system 504 mayinclude a processor, a receiver, and logic for receiving and processinglocation data received from the satellite 406. The network bus 506 maybe any type of network, or combination of networks, known in the art,e.g., local area network, wide area network, intranet, extranet,Internet, etc.

In an embodiment, a cloud consumer, such as client system 404, mayaccess one or more of computer systems 502 a-502 n of the data center500, as well as any other data center (e.g., data centers 410 a-410 n ofFIG. 4) depending on the terms of the client's service agreement, andthe computer systems at each of the relevant data centers executecorresponding applications (e.g., applications 508 a-508 n) and storagedevices (e.g., storage devices 512 a-512 n) pursuant to the computingneeds of the client system 404. In a cloud computing environment, theremay be multiple instances of these applications simultaneously executingacross a distributed number of computer systems. The system providesload balancing techniques to ensure high speed processing according tothe availability of the various computer systems and related resources.An application instance, as described herein, refers to a virtualmachine with specified memory, storage space, and virtual processingcores and units that are defined for a particular platform, such as 32-or 64-bit platform. The network environment may operate via a cloudinfrastructure in which the storage of, and access to, data storage ismanaged by the provider system on behalf of a data owner and/or end user(e.g., client system 404).

As indicated above, a service agreement specifies performancerequirements and related information. A customer who is interested incost savings above other considerations may specify that the lowest costdata centers should be used for the customer's computing services.However, a customer who is more interested in data security than costs,may opt for a data center with higher costs but which has the mosttrusted encryption and security tools available. Further, that samecustomer may require that all data be stored in a data center located inthe United States for security reasons. Yet another customer may befocused on data integrity and require a certain level of redundancy instorage options in the event of a network disruption. In addition, thepreference or desirability of a particular data center may change fromone determination to another based on the current capacity or loadstatus of the data center; thus, the list of data centers employed maybe ‘dynamic.’ These and other factors may be employed in establishing aservice agreement.

The performance validation processes enable network-hosted computingproviders to provide transparency to its customers relating to thelocation and allocation of resources in a cloud computing environment.Turning now to FIG. 6, a flow diagram describing a process for implementthe performance validation processes will now be described in anembodiment. It will be assumed for purposes of illustration, that thenetwork-hosted computing services are initiated between the clientsystem 404 and the data center 410 a, which in turn corresponds to thedata center 500. Further, it is assumed that the communications areconducted at least initially, between the client system 404 and thecomputing system 502 a of the data center 500.

At step 602, the computer system 502 a receives a request from theclient system 404 to access an application hosted by the provider system402. At step 604, the control logic 510 a queries the GPS system 504 forgeographic location information. The geographic location informationrepresents the geographic location (e.g., in longitude and latitude) ofthe particular data center 410 a/500.

At step 606, the control logic 510 a receives the geographic locationinformation of the data center 410 a/500, and at step 608, the controllogic 510 a transmits this geographic location information to the clientsystem 404 and provides access to the requested application (e.g., oneof applications 508 a).

As indicated above, there may be multiple instances of a requestedapplication simultaneously running for a given client system. Theperformance validation processes are configured to track geographiclocations of each of the data centers managed by the network-hostedservice provider for the client system and provide this information tothe client system. For example, as shown in FIG. 7, a location map isprovided to the client system 404 in which there are two currentlyrunning instances for an application (App1). The control logic for eachof the computer systems for which an instance is running may providethis information to the client system, and the application agent 414 maybe configured to populate the location data onto the map. Alternatively,a supervisory control logic program may monitor client system requeststo a particular data center and provide this information to the clientsystem.

As shown in FIG. 7, a first instance is running at a data center 702 inCalifornia. The control logic provides service activity data 704, suchas the application identification and instance, start date and times, aswell as stop date and times. A status of the instance (e.g., stillrunning, and marked as a lightly shaded circle 708) indicates theinstance has not completed at the location, and a status of completed ornot running (e.g., a stop date and time, and marked as a dark circle710) indicates the instance has ended. As shown in FIG. 7, Instance2 forApp1 has ended for the Austin site 712 and has migrated to the Atlantasite 714. This may be caused by various factors, such as lack ofcapacity at one site, a system downtime, or scheduling requirement, toname a few.

As the control logic provides valuable service activity data to theclient system, the performance validation processes enable a consumer,e.g., client system 404, to identify activities that may be conductedoutside of the boundaries of the service agreement. In an embodiment,once the control logic provides the geographic location information tothe client system (as described in step 608), the client system may beprovided with an option to accept or reject the activity (e.g., wherethe activity specifies an application instance 1 will be run at theAustin site). In this manner, the performance validation processes mayrequest approval of the client system (on a case by case basis) beforerunning an instance of an application at a data center not agreed uponin the service agreement.

In addition, as the control logic provides valuable service activitydata to the client system, the performance validation processes enable aconsumer, e.g., client system 404, to identify any non-conformances,e.g., where the activities are currently being conducted are outside thebounds of the service agreement. For example, if an application isrequired to run at a single selected data center, and it is determinedfrom the service activity data that there are instances running at adifferent data center, this information is provided to the client systemvia a user interface, along with an option to contact the performancevalidation processes to alert and correct the non-conformance.

As shown in FIG. 8, a user interface 800 illustrating service activitiesand associated non-conformances is provided. As shown in FIG. 8, thenon-conformances may be defined by a severity value (column 802) inwhich different actions 804 may be taken based on the severity level.What constitutes a severity value may be defined by the user of theclient system, e.g., via the application agent 414. For example, aviolation of the network-hosted computing schedule may be defined as alevel 2 (less severe) violation, while a violation of a network-hostedcomputing site location may be defined as a level 1 (severe) violation.In an embodiment, a level 1 violation may trigger an automatic alarm tothe client system 404, which may then take action such as contacting theservice provider 402.

As indicated above, the performance validation processes may determinegeographic location information according to an alternative embodiment.Turning now to FIG. 9, a process for implementing the performancevalidation processes in an alternative embodiment will now be described.

At step 902, each of the applications at one or more associated datacenters sends its service data, such as customer identification (e.g.,identification of the client system/customer), applicationidentification, and instance identification to the GPS system 504 (e.g.,via the GPS receiver). The GPS 504 uploads the service data, along withits location, to the satellite 406 at step 904. The application agent414 contacts the satellite 406 to obtain the service data and thegeographic location information at step 906, and the application agent414 populates a location map with the service data and locationinformation at step 908. A location map 1000 providing a view of thisservice data and location information is shown in FIG. 10. The servicedata may also include schedule information and a beginning date of theschedule, as shown generally in FIG. 10.

A non-limiting, sample configuration script for implementing theperformance validation processes is provided below:

AppInfo>   <App Name=”DBServer” AppID=”1” CommType=”App/Satellite” /><Instances NoOfInstances=”2” InstanceType=”Static/Dynamic”InstanceContinuity=”yes/no” />  <Instance1> <HostingLocationLongitude=”10” Lattitude=”10”/><HostingScehdule=”Weekday/Daily/HourList/DayList”/> <HostingTimingStart=” 00:30:00 “ End=”00:45:00“ /> <HostingDependancy> <App ID=””Instance=””> <WhatDependancy Code=”1”> </HostingDependancy> </Instance1> <Instance2> <HostingLocation Longitude=”20” Lattitude=”20”><HostingScehdule=”Always/Weekday/Daily/HourList/DayList”> <HostingTimingStart=”00:30:00 “ End=”00:45:00”> <HostingDependancy> <App ID=””Instance=””> <WhatDependancy Code=”2”> </HostingDependancy> </Instance2></AppInfo>

In a further embodiment, the performance validation processes providetrusted information about data center performance histories. Forexample, each data center stores log information regarding systemstatuses in the form of whether a node is running or is down. The loginformation may be stored in storage devices 512 a-512 n. The loginformation may also include a selected node/cluster for hosting a givenapplication instance. In an embodiment, this information may be providedto a trusted third party utility which analyzes the information todetermine which cluster is hosting given an application instance and howfrequently the cluster was running or experiencing downtime. Thisinformation can be provided to the customers to confirm hostingavailability with regard to service agreement requirements.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the disclosure in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the disclosure. Theembodiments were chosen and described in order to best explain theprinciples of the disclosure and the practical application, and toenable others of ordinary skill in the art to understand the disclosurefor various embodiments with various modifications as are suited to theparticular use contemplated.

Further, as will be appreciated by one skilled in the art, aspects ofthe present disclosure may be embodied as a system, method, or computerprogram product. Accordingly, aspects of the present disclosure may takethe form of an entirely hardware embodiment, an entirely softwareembodiment (including firmware, resident software, micro-code, etc.) oran embodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present disclosure may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent disclosure may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present disclosure are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of thedisclosure. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is:
 1. A method, comprising: for each of a plurality ofdata centers in a network-hosted computing environment, receivinggeographic location information from a global positioning systemreceiver associated with a corresponding data center; transmitting thegeographic location information of at least one of the plurality of datacenters to a client system on which an application is running via thenetwork-hosted computing environment, the application running on theclient system under a service level agreement between a user of theclient system and a host provider of the network-hosted computingenvironment; providing the client system with an option, via aninterface, to configure severity values for association with each of aplurality of non-conformance types, with respect to performance of theapplication at a data center, each of the severity values defining aseparate action to be taken; and transmitting service data correspondingto the performance of the application to the client system; wherein theactions include migrating the currently-running application to adifferent data center based on an identification of one of theconfigured severity values with respect to the service data, thedifferent data center selected based on the geographic locationinformation.
 2. The method of claim 1, further comprising: providing ageographic map for the client system; and populating the geographic mapwith the geographic address of the data centers and correspondingservice data associated with service activities specific to the clientsystem only, the service data including an application identificationand an application instance identification.
 3. The method of claim 2,wherein the service data includes application instance start date andtime and application instance stop date and time.
 4. The method of claim2, wherein the service data includes application status including activeand inactive.
 5. The method of claim 2, wherein the service dataincludes application instance migration information.
 6. The method ofclaim 1, further comprising: providing, to the client system, a view ofany application instances specific to the client system that arenon-conformant with terms of the service level agreement.
 7. The methodof claim 1, further comprising: providing an option to the clientsystem, along with the geographic location information of the differentdata center, to accept or reject the different data center with respectto migrating the application in response to a non-conformance.
 8. Themethod of claim 1, further comprising: providing, to the client system,a view of a schedule of applications and application instances andcorresponding geographic locations of data centers; and providing anoption to the client system to accept or reject at least one of the datacenters with respect to the schedule in response to a non-conformance.9. The method of claim 1, wherein geographic location information isreceived from a global positioning system that is communicativelycoupled to a global positioning system satellite.
 10. The method ofclaim 1, wherein the network-hosted computing environment is a cloudcomputing network.
 11. The method of claim 1 wherein service levelagreement specifies that the application is to run on at a single datacenter selected by the user, and one of the non-conformance typesindicates the application is being run at multiple data centers or at adata center not specified in the service level agreement.
 12. The methodof claim 1, wherein the service level agreement specifies that theapplication run within a schedule specified by the user, and one of thenon-conformance types indicates the application is being run at a timethat is outside of the specified schedule.
 13. A computer programproduct comprising a non-transitory computer-readable storage mediumhaving instructions embodied thereon, which when executed by a computer,causes the computer to implement a method, the method comprising: foreach of a plurality of data centers in a network-hosted computingenvironment, receiving geographic location information from a globalpositioning system receiver associated with a corresponding data center;transmitting the geographic location information of at least one of theplurality of data centers to a client system on which an application isrunning via the network-hosted computing environment, the applicationrunning on the client system under a service level agreement between auser of the client system and a host provider of the network-hostedcomputing environment; providing the client system with an option, viaan interface, to configure severity values for association with each ofa plurality of non-conformance types, with respect to performance of theapplication at a data center, each of the severity values defining aseparate action to be taken; and transmitting service data correspondingto the performance of the application to the client system; wherein theactions include migrating the currently-running application to adifferent data center based on an identification of one of theconfigured severity values with respect to the service data, thedifferent data center selected based on the geographic locationinformation.
 14. The computer program product of claim 13, furthercomprising instructions for implementing: providing a geographic map forthe client system; and populating the geographic map with the geographicaddress of the data centers and corresponding service data associatedwith service activities specific to the client system only, the servicedata including an application identification and at least one of: anapplication instance identification; application instance start date andtime; application instance stop date and time; application statusincluding active and inactive; and application instance migrationinformation.
 15. The computer program product of claim 13, furthercomprising instructions for implementing: providing, to the clientsystem, a view of any application instances specific to the clientsystem that are non-conformant with terms of the service levelagreement.
 16. The computer program product of claim 13, furthercomprising instructions for implementing: providing an option to theclient system, along with the geographic location information of thedifferent data center, to accept or reject the different data centerwith respect to migrating the application in response to anon-conformance.